Skip to main content

Packers still ironing out the bugs

In the wake of last Sunday’s misstep in Minnesota, from the sky-is-falling sector of Green Bay Packers fandom comes a reasonable inquiry. Should we be concerned? After the completion of the second week of the National Football League schedule, there are more tricky questions surrounding the Packers than there are reasons to feel confident, let alone invincible. They were beaten by a Vikings team playing without its No. 1 quarterback, and whose best player was an utter non-factor before he left the game with an injury. Making matters worse was Packers quarterback Aaron Rodgers’ getting outplayed by Minnesota QB Sam Bradford, who’d joined the team just two weeks earlier but guided the Vikes’ offense with Rodgers-like efficiency. Rodgers was intercepted once and committed a career-high three fumbles – two when his celebrated pocket instincts sidestepped him and one when he didn’t protect the ball while high-tailing it from the relentless Vikings rush. The loss to Minnesota was the second straight unspectacular performance by the Packers – not a great way to begin a campaign in which they had been regarded among a handful of teams favored to win it all. Their close-shave, season-opening escape in Jacksonville was written off to the Jaguars’ big improvement over last year. But then those improved Jags turned around and got destroyed by San Diego. So, what to make of the Packers heading into Week 3? In what we have come to expect as a normal year, it would be a relief for the Packers to welcome the Detroit Lions to Lambeau Field for this Sunday’s home opener. Instead, there are the lingering remnants of the Lions’ last visit here, when a Packers failed 2-point conversion in the last half-minute preserved an 18-16 Detroit upset win. That, plus the two straight mediocre performances, and a sense of growing parity throughout the league, can give pause to the notion of the Packers’ coming in favored by more than a touchdown. However, it’s instructive to note that but for one unfortunate spot against the Vikings, it may be an altogether different tune being sung today. Trailing 10-7 with a little more than five minutes left in the third quarter, the Packers went for it on fourth-and-2 from the Minnesota 14 rather than kick a game-tying field goal. Say what you will about taking the points when they’re there, but credit coach Mike McCarthy for having the guts to shuck the conventional wisdom and safe call. James Starks appeared to have made the first down – and he did, by one line judge’s spot. But by the other line judge, the one who took the ball and made the spot, he was short by a few inches. It’s the kind of thing that goes your when you’re running hot. As it worked out, it was the Vikings blowing their goofy, oversized Gjallarhorn in the winner’s circle, and the Packers looking up from second place in the NFC North. Good teams overcome dodgy calls and all that, but to anyone who would argue that refs can’t be the sole deciding factor of an outcome, a couple of words that may jog your memory are “Fail Mary.” For all his sub-par plays, Rodgers’ good instincts were still evident on his 10-yard touchdown scramble that brought the Packers to within 17-14. That score came on a drive in which he connected with Jordy Nelson on a sweet 39-yard hookup in the corner, a bomb reminiscent of the old days. Plus, the Packers’ run defense is leading the league. Minnesota linemen got windburn from Mike Daniels and Nick Perry, who were in the Vikings’ backfield as often as Adrian Peterson before he hobbled off the field. Better days for the Pack are almost surely afoot. Although, if they tank again and get stuffed by the Lions, skeptics might feel justified reaching for the panic button. It’s the red one, on the right.